1.4. Fourth Set of Comments

One vendors application converts individual to UTC time. They also move floating recurr to UTC. Syncing unlimited recurrence fails. It also adds Alarms to every event. We found that this application rewrites exceptions as RDates and Exdates. Another vendor’s handling of modifications loses non-time pieces of these exceptions. All-day event creation fails on another vendors application. We also noted that another vendor does not send durations.

With regards to the specific items tested, they noted the following:

1. While verifying two free busy periods, they actually got three free-busy periods noted. So far as they could tell, both forms are valid (i.e. servers & clients are free to coalesce free-busy as they see fit).

2. While testing against one vendor application they noted the following:

   1. The server deleted VALARMs stored with events

   2. Modifications to recurring events caused an internal server error (500 HTTP response)

   3. The server never changes ETags, so a second client isn’t able to sync properly, since it thinks events haven’t changed since previous sync.

   4. The HTTP DELETE request succeeded, but the collection stayed on the server.

   5. The server returned an empty (HTTP 204) response to a valid free-busy-request REPORT.